Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove set bind permissions #7078

Merged
merged 1 commit into from
Dec 19, 2024
Merged

Remove set bind permissions #7078

merged 1 commit into from
Dec 19, 2024

Conversation

ptodev
Copy link
Contributor

@ptodev ptodev commented Dec 18, 2024

Porting this fix from Alloy to Agent. It is requested by users whose Agents fail to start due to a "operation not permitted" error.

The reason why Agent requests cap_net_bind_service is that it listens on port 80 by default. Thus, if someone configures Alloy with the non-root user with ID 473, they'd need that capability. However, this is As the Alloy issue states, Docker has been enabling that capability by default for a long time now. So even for non-root users we wouldn't really need to set it.

Since only non-root users would encounter this, and non-root support is experimental, it's ok to remove the capability anyway.

@ptodev ptodev force-pushed the ptodev/remove-libcap branch from 98ace31 to 4acfc13 Compare December 19, 2024 11:28
@ptodev ptodev merged commit 2ed5557 into main Dec 19, 2024
10 checks passed
@ptodev ptodev deleted the ptodev/remove-libcap branch December 19, 2024 11:37
@github-actions github-actions bot added the frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed. label Jan 19, 2025
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 19, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants